Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@plane/api/customers/base.py`:
- Around line 84-97: Rename the affected customer resource methods to use
standard CRUD verbs: change delete_by_external_id to delete in
plane/api/customers/base.py lines 84-97; rename the bulk set method to create in
plane/api/customers/property_values.py lines 42-61; rename the work-item linking
method to create in plane/api/customers/work_items.py lines 54-78; and rename
the unlinking method to delete in plane/api/customers/work_items.py lines
80-102. Preserve each method’s existing behavior and parameters.

In `@plane/api/customers/property_values.py`:
- Around line 27-40: Add response DTOs for customer property values and update
both list() and retrieve() to validate _get() results through the appropriate
DTO model_validate() calls before returning them. Preserve the documented empty
mapping behavior where applicable, while ensuring malformed responses are
rejected before callers can access unexpected shapes or invoke .get().

In `@tests/unit/test_customers.py`:
- Around line 53-65: Update test_list_customers_with_params and
test_list_customers_paginates to create at least two customers before listing,
assert the expected page size and pagination state unconditionally, and clean up
the created customers afterward. Reuse the existing customer creation and
deletion helpers/fixtures in the test suite.
- Around line 143-146: Update the cleanup blocks in the customer tests,
including the repeated cleanup handlers, to suppress only the expected
not-found/404 exception from delete operations. Re-raise all other exceptions so
failures deleting customers, properties, requests, or work items are visible
instead of silently ignored.

---

Outside diff comments:
In `@plane/api/customers/requests.py`:
- Around line 17-35: The customers.requests.list method changes its return
contract to PaginatedCustomerRequestResponse; either preserve the previous
list-compatible contract or explicitly release this as a breaking change. If
retaining the new pagination model, update pyproject.toml to the next minor
version (such as 0.3.0); otherwise adjust list to return the prior type and
behavior.
- Around line 48-70: Update the create method in the customer requests client to
accept only CreateCustomerRequest and normalize any legacy CustomerRequest input
into that model before calling _post. Ensure the payload comes exclusively from
the normalized CreateCustomerRequest.model_dump(exclude_none=True), preventing
response-only extra fields from being submitted.